Skip to content

feat: add support for step-level xray-test-case annotations - #23

Merged
incident-recipient merged 13 commits into
google:mainfrom
atatur:feat/parse_step_comments
Jul 29, 2026
Merged

feat: add support for step-level xray-test-case annotations#23
incident-recipient merged 13 commits into
google:mainfrom
atatur:feat/parse_step_comments

Conversation

@atatur

@atatur atatur commented Jul 20, 2026

Copy link
Copy Markdown
Contributor
  • implement extraction of step-level #@xray-test-case annotations from TestCase step comments.
  • track and assigns step execution statuses to step-level test cases (PASSED, FAILED, or BLOCKED if a previous step failed).
  • add "BLOCKED" to the default list of supported Xray execution statuses.
  • configure antlr4-maven-plugin to correctly locate and compile grammar files from src/test/antlr4.
  • add comprehensive unit tests to verify both successful scenario runs and partial scenario failures.

@atatur atatur changed the title feat: add support for step-level xray-test-case annotations [DRAFT] feat: add support for step-level xray-test-case annotations Jul 20, 2026
if (commentTrimmed.startsWith("#")) {
commentTrimmed = commentTrimmed.substring(1).trim();
}
if (commentTrimmed.startsWith("@")) {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand why we're processing tags the same way we would comments. The tags are in the TaggedTestCase object. It makes more sense to try to cast to this type and get the set of tags than to re-parse it out of the metadata.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done d50e3bf

@atatur
atatur force-pushed the feat/parse_step_comments branch from df3e967 to 69d342e Compare July 21, 2026 20:55
  - implement extraction of step-level `#@xray-test-case` annotations from TestCase step comments.
  - track and assigns step execution statuses to step-level test cases (PASSED, FAILED, or BLOCKED if a previous step failed).
  - add "BLOCKED" to the default list of supported Xray execution statuses.
  - configure antlr4-maven-plugin to correctly locate and compile grammar files from src/test/antlr4.
  - add comprehensive unit tests to verify both successful scenario runs and partial scenario failures.
@atatur
atatur force-pushed the feat/parse_step_comments branch from 69d342e to 5b19fba Compare July 21, 2026 21:00
atatur added 9 commits July 21, 2026 23:38
  - add Google Guava dependency to resolve missing 'com.google.common.base' packages in the build environment.
  - add enum StepStatus, XrayTestTag.
  - start to use XrayTestTag instead of string values.
  - move tag constraint checking to a separate private helper method 'verifyTestItemSize'.
  - remove additional checks from the step tags processing stage.
  - deduplicate identical annotations within a single step using a HashSet.
  - consolidate test results when multiple steps map to the same Xray test case key.
  - implement `mergeStepTestItems` to prioritize and retain the most significant execution status (e.g., FAILED over PASSED) for duplicated test keys.
  - add a unit test to verify the deduplication and status consolidation logic for duplicate step-level comments.
@atatur atatur changed the title [DRAFT] feat: add support for step-level xray-test-case annotations feat: add support for step-level xray-test-case annotations Jul 23, 2026
@incident-recipient
incident-recipient merged commit 7000762 into google:main Jul 29, 2026
6 checks passed
@atatur
atatur deleted the feat/parse_step_comments branch July 29, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants